[Server] Ability to set custom protocol version #117
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ineersa
requested review from
CodeWithKyrian,
Nyholm and
chr-hertel
as code owners
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added ability to set custom protocol version.
This enables usage of clients which doesn't support newest MCP version and will allow to change schema version in future.
Motivation and Context
Some clients doesn't support newest version but work perfectly fine with 90%+ of SDK functionality.
This allows us at least for now use of those clients, at least while Schema Versioning won't be resolved.
How Has This Been Tested?
Unit test.
Jetbrains AI Assistant
Breaking Changes
No breaking changes
Types of changes
Checklist
Additional context